Miscellaneous sphinx fixes #1365
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
pytest failures are all |
AdamRJensen
reviewed
Jan 23, 2022
|
I'm in favor of merging this. I haven't reviewed all the changes so I won't indicate "approve". As a side note, I think the "Contributing" page is too long and should be organized into a set of pages. Definitely a different issue. |
|
Forgot about this. I'll merge tomorrow unless objections are raised. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Tests addedUpdates entries todocs/sphinx/source/api.rstfor API changes.Adds description and name entries in the appropriate "what's new" file indocs/sphinx/source/whatsnewfor all changes. Includes link to the GitHub Issue with:issue:`num`or this Pull Request with:pull:`num`. Includes contributor name and/or GitHub username (link with:ghuser:`user`).New code is fully documented. Includes numpydoc compliant docstrings, examples, and comments where necessary.Two things:
The README file has this line:
It's not broken now, but will be as soon as we release 0.9.1. I guess we should leave that until we're ready to make the next release?
The only remaining
latestlinks are in the two markdown files in https://github.com/pvlib/pvlib-python/tree/master/.github. I think it makes sense to leave those aslatest.